import can't check account names / account declarations not affecting sibling files

[simonmichael]

Reported in chat: hledger import -s does not seem to see account declarations in the main journal, and will wrongly complain that account names are not declared. Current workaround: don't use -s with import, eg you could do this instead: hledger import ... && hledger check -s

[simonmichael]

I believe this is related:

commodity ""
account a
account b

2023-01-01
  (a)   1

2023-01-02
  (b)   2

$ hledger -f a.j  -f b.j print -s
hledger: Error: /Users/simon/src/hledger/b.j:2:
  | 2023-01-02
2 |     (b)               2
  |      ^

Strict account checking is enabled, and
account "b" has not been declared.
Consider adding an account directive. Examples:

account b
account b    ; type:A  ; (L,E,R,X,C,V)

Ie, account directives are not affecting a sibling file. This is odd because https://hledger.org/dev/hledger.html#directive-effects says account should affect all files, not just the current one.

[simonmichael]

And, hledger -f a.b -f b.j check accounts passes, but hledger -f a.b -f b.j check accounts -s does not.

[simonmichael]

We'd like to be able to do strict account name checking on the generated transactions before proceeding with an import. Eg because we want to know

• when categorisation rules are incomplete and transactions involving "expenses:unknown" or "income:unknown" are generated
• when we accidentally changed the rules so as to generate undeclared account names
• when we forgot to update csv rules after changing account names and account declarations