Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add logic for optional chaining #21

Merged
merged 5 commits into from Oct 25, 2023

Conversation

nadiapadalka
Copy link

@nadiapadalka nadiapadalka commented Oct 23, 2023

Added logic for optional Chaining

  • added tests as well
  • now any warnings do not appear

Addressing #20

Copy link
Member

@TwitchBronBron TwitchBronBron left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks pretty good. I just have a few questions/suggestions.

src/parser/Parser.ts Outdated Show resolved Hide resolved
test/e2e/BrsComponents.test.js Outdated Show resolved Hide resolved
test/brsTypes/components/RoDateTime.test.js Outdated Show resolved Hide resolved
src/parser/Parser.ts Show resolved Hide resolved
@TwitchBronBron
Copy link
Member

@nadiapadalka looks like the build is currently failing. Can you fix the issues?
image

Here are all the commands we run as part of the build.

- run: npm ci
- run: npm run build
- run: npm run lint
- run: npm run prettier
- run: npm run test
- run: npm run publish-coverage

@nadiapadalka
Copy link
Author

@TwitchBronBron fixed

@TwitchBronBron TwitchBronBron merged commit 7569e86 into rokucommunity:master Oct 25, 2023
2 checks passed
@nadiapadalka
Copy link
Author

@TwitchBronBron Hi! The question to you: how can we see this change in our testing environment? Should we make the new release with this PR included or what?

@TwitchBronBron
Copy link
Member

TwitchBronBron commented Nov 8, 2023

I actually just cut a new release this morning that includes this change. If you upgrade to @rokucommunity/brs v0.45.2, you should see the change.

I apologize for taking so long to get the release out. We were waiting to get a few additional fixes in, and then I got super busy the past few days.

Thanks again for submitting this fix!

@nadiapadalka
Copy link
Author

I actually just cut a new release this morning that includes this change. If you upgrade to @rokucommunity/brs v0.45.2, you should see the change.

I apologize for taking so long to get the release out. We were waiting to get a few additional fixes in, and then I got super busy the past few days.

Thanks again for submitting this fix!

oh, good to hear! thanks!

@nadiapadalka
Copy link
Author

Next question - maybe you can give the advice to me how to upgrade the version correctly? I tried different steps, but seems they are not working

@TwitchBronBron
Copy link
Member

This is a fork of the original project, so you might need to change a reference or two in your code depending on how you're running it. Are you using brs directly or is it being used from another tool?

You might need to do this:

npm uninstall brs
npm install @rokucommunity/brs

If you're using the brs cli directly, that's probably all you need to do

@nadiapadalka
Copy link
Author

Thanks! But any succcess from my side. Maybe you can try from your side to run any test? Because everything I see now is like this
Screenshot 2023-11-10 at 08 52 50

@TwitchBronBron
Copy link
Member

TwitchBronBron commented Nov 10, 2023

Are you using roca for your tests? We don't have any control of that project, and I don't believe there's currently a way to override their embedded version of brs to use Rokucommunity/brs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants