bcgov / bcgov/entity

Filings UI: Future Effective regular filings can't display POA/Court order - filing.data object issue

Open
#23,651 7 comments 0 reactions 0 assignees View on GitHub
Entities Team Priority3
Dominant language
JavaScript
Stars
23
Forks
62
Avg merge
24m
Merged PRs (30d)
1

Description

For 2 regular filing types: Alteration and Voluntary dissolution, they can be filed Future Effective.
The ledger doesn't display the POA/Court order now.
This is because the "get filings" call returns an array of filings with redacted data and doesn't have a filing.data object yet.

Sample VD:
https://github.com/user-attachments/assets/0a737322-b7cc-4ae5-81f4-885f16bbb17e
https://dev.business.bcregistry.gov.bc.ca/BC0871344?filing_id=151370&accountid=3040

FE IA/ContIn is good because for a bootstrap filing, the get filings call returns a single filing with all JSON data.

Contributor guide

No contributing guide indexed for this repository

Research direction

Inspect the Filings UI ledger and the get filings response for future-effective Alteration and Voluntary dissolution filings, focusing on when filing.data is absent. Compare these cases with FE IA/ContIn bootstrap filings. Done means the ledger displays the POA or Court order for both affected regular filing types.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.