SDK 4.4.0 #39
Replies: 3 comments 6 replies
-
|
I'm surprised to find that I can choose between Global and Scoped application when initializing a new project. Does that mean Global scope solutions are now finally supported? If so, I think it deserves some space in the release notes, that is a great addition :) |
Beta Was this translation helpful? Give feedback.
-
|
Good work on the dev server! Guess I can now look into retiring my trusty vite dev server I have been using with my SDK applications. @bryce-godfrey saying that, did we ever get anywhere with native tailwind support? I still only have support for it via triggering a manual postcss build in the now.prebuild.mjs file. Having it work natively via the tailwind rollup plugin would be ideal |
Beta Was this translation helpful? Give feedback.
-
|
Great work on dev server! that's exactly what we needed, we have built custom tooling for similar challenges. Can't wait to get hands dirty. One questions related all the cool things SDK is delivering, will there ever be "unit-tests" mock libraries for server-side APIs? Is there already in the ecosystem? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
@servicenow/sdk— Release NotesVersion:
4.4.0Availability: npm — https://www.npmjs.com/package/@servicenow/sdk
🚀 Overview
Version 4.4.0 fixes some bugs and adds a new dev server capability for front end UI building with the SDK, and some internal support for future version of Build Agent!
New Features
Global App Support
Global apps are now supported by the SDK, see this announcement here: #40 for more information on that.
Front-End Dev Server
A highly requested feature — the dev server drastically reduces build cycles and enables rapid UI development without needing to deploy to an instance. Requests are proxied to the ServiceNow instance defined in your auth credentials.
Getting started:
sdk initusing thereactorvuetemplatenpm run devRequirements:
@servicenow/isomorphic-rollup>=1.2.14@servicenow/sdk>=4.4.0now.dev.mjspresent in your project (generated duringinit)ServiceCatalog & Flows
Add support between Flows and ServiceCatalog in Fluent for interacting with catalog variables and actions in Flows, and for Catalog Items to trigger Flows!
getCatalogVariablesaction in FlowssubmitCatalogItemRequestaction in FlowsSee sdk-examples Flow samples
Changes
durationfield forSlarequestMethodonCatalogItemandCatalogItemProducernot serializing properlyprotectionPolicytoACLtableDefaultLanguagetonow.config.jsonto support setting language on table column labelsNOTE: Many APIs were not strictly enforcing that extra properties could not be defined on the API, which caused some usage errors around mispelling properties or thinking they can add a property and it will be added to the build output.
For example this would not produce an error:
This will now produce an error diagnostic that
randomPropertydoes not exist as an option onProperty! This may introduce a build error for existing projects when upgrading to4.4.0, but these properties were being ignored during build causing false positives.This discussion was created from the release SDK 4.4.0.
Beta Was this translation helpful? Give feedback.
All reactions