correctly determine the vis instance in all cases #351
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
3_Test
will lead to the case, that adapter-react-v5 will determine the instance as3
, because of https://github.com/ioBroker/adapter-react-v5/blob/bae98e05d9d0df4443b59bda6b7ac08f3135bf4f/src/GenericApp.js#L139 is using the first char inwindow.location.search
if it is a number, becausevis-2
url is build like http://localhost:8082/vis-2/?3test#default but does not containinstance=
in url0
, this is edgy but also caught here, else it would be enough to just pass0
. Instead the backend is injecting the real instance number into the window object leading to an accurate instance detection