v1.0.0 🎉 #377
vobu
announced in
Announcements
v1.0.0 🎉
#377
Replies: 2 comments
-
@vobu How do we pass authentication details such as username and password? |
Beta Was this translation helpful? Give feedback.
0 replies
-
you can do this by providing it as an ENVIRONMENT variable. E.g. you can create a file named ".env" within your working directory with the contents: wdi5_username=[email protected] For MultiRemote Access add the name of the remote. You can find further information here: https://ui5-community.github.io/wdi5/#/authentication?id=credentials |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
v1.0.0
Here we are, with the first major release of
wdi5
!It includes a plethora of features and changes. Let's dive in 🤿
🔐 Authentication support
Long in the making, now here: configure
wdi5
to authenticate against📖 https://ui5-community.github.io/wdi5/#/authentication
Authentication is config-only, so no changes in test code required 😎
🤲 UI5 Managed Object API alignment
In addition to the UI5 Control API alignment, now the managed objects in
wdi5
-/Node.js-scope are also aligned:more on this in https://ui5-community.github.io/wdi5/#/usage
🗑️ deprecation of the
wdi5
-specificurl
configuration optionthe always mandatory
basicUrl
and thewdi5
-specificurl
was confusing, so it now isbaseUrl
only→ less config clutter
📖 https://ui5-community.github.io/wdi5/#/configuration?id=url-deprecated
♻️ no worries, legacy support is in place, so all your configs keep on working
📝 documentation enhancements
💑 Thanks a ton to all contributors, testers and supporters all over UI5-land!
This one's for you! 👏 ✌️
PS: expect next releases to follow a more proper
major
-minor
-patch
semantic versioning strategy. So far, we stuck to0.9.x
patch releases in order to prep for this1.0
, which is now done. So true semantic versioning it will be from now on.Beta Was this translation helpful? Give feedback.
All reactions