<@U01ADSJ1D5H> I’m noticing an issue with the UI o...
# dev-frontend
s
@Artem Astapenko I’m noticing an issue with the UI on master — I ran a fresh version of the app (
docker-compose down && docker-compose down --volumes && docker-compose --env-file .env.dev -f docker-compose.yaml -f docker-compose.dev.yaml up
) but the UI breaks on the onboarding page with the exception in the screenshot. as far as i can tell all the network calls are returning appropriately. Do you know what the issue is here?
a
1 second
looking
hm, a bit strange as I just ran fresh version of my changes that were just based on master.
This error means that some entity did not return id ( or what is used as primary key )
s
it could be that the UI is expecting a spec ID somewhere? (which were removed while this PR was approved but not merged)
a
yep. Thats what I was writing right now.
DestinationImplementationResource
and
SourceImplementationResource
expect their ids. So if they were removed and those changes are already merged - its possible that something may not work
but what is strange - that I do not have such problems with fresh master merged into my branch. Sorry its a bit late here, so I can’t take a look on it right now … but if error is still there by the morning - I will fix.
👍🏼 1
s
https://github.com/airbytehq/airbyte/pull/572 i think this PR should fix the issue